![Beans Beans can be any Java object, or termed as Plain Old Java Object or POJO .] They doesn’t have to extend any class, implement any interface, or contain any annotations. It has 4 attributes name, type, alias, scope. If we were writing a plug-in and wanted the plug-in to define its own ObjectFactory then Ex : <bean type="com.opensymphony.xwork2.ObjectFactory" alias="myFactory“ class="com.mycompany.MyObjectFactory" /> Beans can be register directly with the container by implementing com.opensympony.xwork2.config.ConfigurationProvider interface and specifying your class in web.xml](https://image.slidesharecdn.com/krazykoderstruts2plugins-101018045326-phpapp01/85/Krazykoder-struts2-plugins-8-320.jpg)
Krazykoder struts2 plugins
- 1. Struts 2 Plug - ins
- 2. Plug-ins Overview Plug-in includes the software ingredients to enable features that weren’t in original code base. Typically designed to add custom interceptors and results to the framework. Provide a variety of configuration options. Runtime plug-in elements that can be modified are Bean, Constant, Package / Namespace, Interceptor / Result, Exception.
- 3. Common Plug-ins Plug-in range from connecting to dependency-injection frameworks to providing hooks into look-and-feel libraries. SiteMesh Is a web page look-and-feel, layout, and navigation framework. Provides filters for both FreeMarker and Velocity templates. Standard filter chain optionally starts with the ActionContextCleanUp filter, followed by other desired filters. Purpose of ActionContextCleanUp is to provide SiteMesh integration. Contd…..
- 4. Common Plug-ins Ex : Web.xml entries to add SiteMesh filters. <filter> <filter-name>struts-cleanup</filter-name> <filter-class> org.apache.struts2.dispatcher.ActionContextCleanUp </filter-class> </filter> <filter> <filter-name>sitemesh</filter-name> <filter-class> org.apache.struts2.sitemesh.FreeMarkerPageFilter </filter-class> </filter> Contd…..
- 5. Common Plug-ins Tiles : Allows developers to build templates for application user interfaces. Tiles –default package extends struts-default package so extending tiles-default we can inherit all elements from struts-default package. Ex : configure web.xml to use Tiles plug-ins. <context-param><param-name> org.apache.tiles.impl.BasicTilesContainer.DEFINITIONS_CONFIG </param-name><param-value>/tiles/myTiles.xml</param-value> </context-param> ... <listener><listener-class> org.apache.struts2.tiles.StrutsTilesListener </listener-class></listener> Contd…..
- 6. Common Plug-ins JFreeChart Allows an action to return generated charts and graphs to be included in web page. Ex : Use jfreechart-default package in our xml file. <struts> <package name="charts“ namespace="/charts"extends="strutsdefault , jfreechart-default"> <action name="chartScreen"> <result>/jsp/chart.jsp</result> </action> <action name="chart" class="com.strutsschool.action.CreateChart"> <result type="chart"> <param name="width">400</param> <param name="height">300</param> </result> </action> </package> </struts> Contd…..
- 7. Internal Component System It builds and configures the framework. Manages the life cycle of the components and wires them together with other components and configuration. Two types of objects that can be registered with the inject framework. Beans Constants
- 8. Beans Beans can be any Java object, or termed as Plain Old Java Object or POJO .] They doesn’t have to extend any class, implement any interface, or contain any annotations. It has 4 attributes name, type, alias, scope. If we were writing a plug-in and wanted the plug-in to define its own ObjectFactory then Ex : <bean type="com.opensymphony.xwork2.ObjectFactory" alias="myFactory“ class="com.mycompany.MyObjectFactory" /> Beans can be register directly with the container by implementing com.opensympony.xwork2.config.ConfigurationProvider interface and specifying your class in web.xml
- 9. Constants Simple configuration settings that can be injected into beans. Simple as a name/value pair. Constants defined by the framework can be overridden by plug-ins, and further overridden by application configuration. Constants are loaded in following order. 1. web.xml init parameters for the Struts filter 2. default.properties in the Struts JAR 3. struts.properties in WEB-INF/classes 4. struts-plugin.xml in each plug-in JAR 5. struts.xml in WEB-INF/classes
- 10. Done! Click the icon at the bottom to proceed!